NO-JIRA: Add DevPreviewNoUpgrade as a featureset#1825
NO-JIRA: Add DevPreviewNoUpgrade as a featureset#1825openshift-merge-bot[bot] merged 4 commits intoopenshift:masterfrom
Conversation
|
Hello @deads2k! Some important instructions when contributing to openshift/api: |
7f2ce3c to
6bfc356
Compare
6bfc356 to
3ede02b
Compare
3ede02b to
28f074c
Compare
|
/retest |
|
@deads2k: This pull request explicitly references no jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
28f074c to
54c24d1
Compare
b18f8d8 to
27c4944
Compare
JoelSpeed
left a comment
There was a problem hiding this comment.
Do we have some criteria by which a developer would decide if their feature is Dev vs TechPreview? And do we have somewhere where we can document that?
| // +optional | ||
| // +kubebuilder:validation:XValidation:rule="oldSelf == 'CustomNoUpgrade' ? self == 'CustomNoUpgrade' : true",message="CustomNoUpgrade may not be changed" | ||
| // +kubebuilder:validation:XValidation:rule="oldSelf == 'TechPreviewNoUpgrade' ? self == 'TechPreviewNoUpgrade' : true",message="TechPreviewNoUpgrade may not be changed" | ||
| // +kubebuilder:validation:XValidation:rule="oldSelf == 'DevPreviewNoUpgrade' ? self == 'DevPreviewNoUpgrade' : true",message="DevPreviewNoUpgrade may not be changed" |
There was a problem hiding this comment.
I don't remember there being CEL here, but, LGTM. Is it new?
There was a problem hiding this comment.
I don't remember there being CEL here, but, LGTM. Is it new?
"while you were out" :)
| counts[featureGate] = counts[featureGate] + 1 | ||
| } | ||
| for _, featureGate := range byFeature.disabled.List() { | ||
| counts[featureGate] = counts[featureGate] + 0 |
There was a problem hiding this comment.
Ineffective assignment? Did you mean add 0?
There was a problem hiding this comment.
Ineffective assignment? Did you mean add 0?
I think so. Just making it clear how to bump in the list and nice and parallel. Similar blocks exist in other repos that do shift priority.
| crdFilename := strings.ReplaceAll(crdFilenamePattern, "MARKERS", fmt.Sprintf("-%s", utils.ClusterProfileToShortName(clusterProfile))) | ||
| clusterProfileShortName, err := utils.ClusterProfileToShortName(clusterProfile) | ||
| if err != nil { | ||
| panic(fmt.Sprintf("unrecognized clusterprofile name %q: %w", clusterProfile, err)) |
There was a problem hiding this comment.
Why is this a panic rather than failing gracefully? Is this user in put or a code problem?
| crdFilename := strings.ReplaceAll(crdFilenamePattern, "MARKERS", fmt.Sprintf("-%s-%s", utils.ClusterProfileToShortName(curr.clusterProfile), curr.featureSet)) | ||
| clusterProfileShortName, err := utils.ClusterProfileToShortName(curr.clusterProfile) | ||
| if err != nil { | ||
| panic(fmt.Sprintf("unrecognized clusterprofile name %q: %w", curr.clusterProfile, err)) |
There was a problem hiding this comment.
As above, should this really be a panic?
27c4944 to
cc7b693
Compare
cc7b693 to
9ab6ed1
Compare
774b4ca to
de5d2ab
Compare
de5d2ab to
17878f0
Compare
|
/retest-required |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: deads2k, JoelSpeed The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest |
2 similar comments
|
/retest |
|
/retest |
|
@deads2k: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build ose-cluster-config-api-container-v4.16.0-202404181209.p0.g21822c8.assembly.stream.el9 for distgit ose-cluster-config-api. |
Some features were getting delivered as devpreview and created their own custom gating mechanism which is not automatically tracked by our tooling. This makes it easy to add featuregates as dev preview without causing rippling impacts for all API authors.
Once we merge this, we must create a test job to show it working.